Open
Conversation
msosnicki
commented
Sep 30, 2025
|
|
||
| ## Abstract | ||
|
|
||
| In the Smithy 2.0 specification enums and unions are treated as strictly **open**: adding a member is always treated as a backward‑compatible change and clients are expected to handle unknown members at runtime. This RFC proposes to update the spec and loosen the strict requirements around open enums and unions, acknowledging the fact that for some use cases and protocols it may not be desireable. It will also align the spec closer to reality, as smithy4s do not follow the current spec. |
Contributor
Author
There was a problem hiding this comment.
Currently the smithy-trait-codegen also do not follow the spec, see here
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Background
Proposal to loosen the enum and union openness requirement in the smithy spec
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.